|
The Build Applet Tab This is where you decide how and where to build the button applet. Getting your applet up and running on the internet is very easy. Just follow these simple steps:
If you still can't get your applet running, see the Troubleshooting section. Enter the folder where you want to create the Button Applet: This specifies the folder where the Button Applet will be built. 1 Cool Button Tool will copy all the files neccessary for running the button applet into this folder, including an HTML file (named projectname.html), the BtnPlayer.class file, and all the bitmaps and sound files required by the applet.   (see the Overview for more information) After the applet has been built just copy the contents of this folder to your web server.   Nothing further is neccessary for the applet to run. Remember, 1 Cool Button Tool applets will not run over the internet unless you have purchased a registration number! Applet Size This information box tells you the total size of the button applet in kilobytes (KB).   That is, how much data will have to be downloaded to run the applet. The applet size is different for Netscape Navigator and Internet Explorer because 1 Cool Button Tool creates a compressed Cabinet file (.cab) which only Internet Explorer can read.   1 Cool Button Tool can also put bitmap and sound files into the Cabinet archive, futher reducing the size of the download.   Netscape Navigator does not support compressed Java applets. The applet size includes the HTML file, the BtnPlayer.class file (or Cabinet file for IE) and any bitmap or sound files required by the applet. Automatically generated HTML code: This is the HTML code that describes the button project.   The Java program (BtnPlayer.class) reads this information, decodes it, and "plays" the button project inside the browser. Everything neccessary to describe the button project is in the HTML code, not in the BtnPlayer.class file. The BtnPlayer.class file is the same for all button applets. Copy HTML to Clipboard: Copies the HTML code to the clipboard.   This allows you to easily copy and paste a button applet into another HTML file. Be aware that the HTML file you are pasting the code into must be in the same folder as the BtnPlayer.class file. Preload Bitmaps: Specifies whether all the bitmaps are downloaded before the button applet starts running.   If this option is checked, there will be a longer initial delay before the applet starts running.   If this option is not checked, bitmaps will be displayed progressively as they are being downloaded. Preload Sounds: Specifies whether all the sounds are downloaded before the button applet starts running.   If this option is checked, there will be a longer initial delay before the applet starts running.   If this option is not checked, sounds will not be downloaded until they are played.   This can result in an annoying delay the first time a sound is played. Include content in Cabinet File: (Internet Explorer only) Specifies whether to use a Cabinet (.cab) file or not. If this option is checked the BtnPlayer.class file and any preloaded content will be put inside the Cabinet file, and the Cabinet file will be named projectname.cab.   If this option is not checked only the BtnPlayer.class file will be put inside the Cabinet file, and the Cabinet file will be named BtnPlayer.cab. . Note for Internet Explorer users: The Cabinet file serves the same purpose as the BtnPlayer.class file.   If the HTML file is not in the same folder as the Cabinet file, the button applet will not run. Build Applet This tells 1 Cool Button Tool to copy all the files neccessary for running the button applet into the output folder, including an HTML file (named projectname.html), the BtnPlayer.class file, and all the bitmaps and sound files required by the applet. The applet is now ready to run.   All you need to do is copy the contents of this folder to your web server.   Nothing further is neccessary for the applet to run. Remember, 1 Cool Button Tool applets will not run over the internet unless you have purchased a registration number! Test Applet Runs the finished button applet in your default browser.   The Test Applet button will always re-build the applet before running it. You should close the browser after testing the applet because some browsers cache the applet in memory.   This means that the next time you test the applet it will appear not to have changed.   Shift-Reload on Netscape Navigator 3 (or later) will force the applet to be reloaded.   Control-Refresh on Internet Explorer 4 (or later) will force the applet to be reloaded.   |